A method of assessing rework for implementing software requirements changes

Software development is often affected by user/system requirements changes. To implement changes, a system which being developed needs to be reworked. However, the term ?Rework? has not been clearly defined in literature. Depending on complexity of amount rework required varies from some software module modifications non-trivial alteration design system. The effort associated with such obviously will vary too. date, there scant research assessment, and relationship between it change estimation hardly understood. In this paper, we present definition for rework, describe method assessing implementing Our consists three stages: namely (i) identification; (ii) analysis; (iii) assessment. demonstrate practicality that enables developers compare different options available identify one less invasive requires lesser design, explain our concept use running example.